Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes for kenwood live #1067

Merged
merged 2 commits into from
Jun 18, 2024
Merged

Fixes for kenwood live #1067

merged 2 commits into from
Jun 18, 2024

Conversation

kk7ds
Copy link
Owner

@kk7ds kk7ds commented Jun 18, 2024

  • kenwood v71: Fix long-standing valid_bands issue
  • Fix tuning step when bandplan is invalid

Somehow this driver has never had valid_bands defined?!

Fixes #11386
Right now we will choose the tuning step for a new edit from the
bandplan, even if that doesn't work for the frequency entered.
Ironically, the most common frequency in the NA bandplan (146.520)
would choose a step of 25kHz, which isn't actually aligned. Radios
that really care about this (i.e. kenwood live radios) will balk at
146.52 at 25kHz, allow it at 20kHz, and allow 146.50 at 25kHz.

This makes memedit use the band plan step if it is valid for the
entered frequency, else fall back to the minimum-viable logic that
we use when there is no bandplan step.

Fixes #11391
@kk7ds kk7ds merged commit 4b0476d into master Jun 18, 2024
6 checks passed
@kk7ds kk7ds deleted the kenwood_fixes branch June 18, 2024 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant